Skip to content

Add user-facing configuration reference#1692

Draft
st0012 wants to merge 1 commit intoruby:masterfrom
st0012:docs/configuration
Draft

Add user-facing configuration reference#1692
st0012 wants to merge 1 commit intoruby:masterfrom
st0012:docs/configuration

Conversation

@st0012
Copy link
Copy Markdown
Member

@st0012 st0012 commented May 4, 2026

Summary

Adds doc/configuration.md, a single-page reference covering how to configure RDoc.

  • The four configuration mechanisms — .rdoc_options, RDoc::Task, .document, and the RDOCOPT env var — with when to use each, syntax, and a worked example.
  • A "name cheat sheet" flagging the ten cross-mechanism naming caveats (e.g. --main vs main_page vs rdoc.main; --output/op_dir/rdoc.rdoc_dir; --template having no portable YAML form).
  • A grouped options reference (What to document, Appearance, Dev/preview, Cross-references, Output/format, I18n) with each option's CLI flag, .rdoc_options key, RDoc::Task attribute, effective default, and notes.
  • Worked examples: minimal gem setup, Rakefile equivalent, footer_content for the Aliki theme, and combining .document + exclude + --no-skipping-tests for scope tuning.

Defaults sourced from RDoc::Options#init_ivars and RDoc::Options#finish (which post-processes a few like op_dir'doc' and rdoc_include[project root]); RDoc::Task defaults from RDoc::Task#defaults (which differs in places, e.g. rdoc_dir = 'html').

The file lives under doc/ so it ships with RDoc's own generated documentation.

A user-facing configuration reference for RDoc covering the four
configuration mechanisms (`.rdoc_options`, `RDoc::Task`, `.document`,
`RDOCOPT`), a name cheat sheet flagging the nine cross-mechanism
naming mismatches, and a grouped options reference with defaults
sourced from `RDoc::Options#init_ivars`.
@st0012 st0012 requested a deployment to fork-preview-protection May 4, 2026 09:47 — with GitHub Actions Waiting
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant